Information processing apparatus, information processing system, information processing method and recording medium

ABSTRACT

An information processing apparatus communicably connected with an intermediary device capable of communicating with at least one device, the information processing apparatus including: circuitry configured to receive, from a terminal operated by a user, identification information that the terminal has acquired from the extraneous source; and transmit a request for execution of a process associated with the acquired identification information to the intermediary device, the request for execution causing the intermediary device to execute the process according to the request for execution to control the device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of U.S. application Ser.No. 16/550,360, filed Aug. 26, 2019, which is based on and claimspriority pursuant to 35 U.S.C. § 119(a) to Japanese Patent ApplicationNo. 2018-170602, filed on Sep. 12, 2018, in the Japan Patent Office, theentire disclosure of which is hereby incorporated by reference herein.

BACKGROUND Technical Field

The present invention relates to an information processing apparatus, aninformation processing system, an information processing method andrecording medium.

Description of the Related Art

An improvement in work efficiency can be expected by utilizing varioustypes of devices. For example, by projecting or displaying data storedin a personal computer (PC) or the like, using a device such as aprojector or an electronic whiteboard, information sharing can beefficiently performed in work.

However, an operation of each device has become complicated due toadvancement of functions or the like and a time required to learn how tooperate the device has been extended. In addition, a fact that a userinterface differs depending on the type of device or difference inmanufacturers also extends learning of how to operate the device.

SUMMARY

Example embodiments of the present invention include an informationprocessing apparatus communicably connected with an intermediary devicecapable of communicating with at least one device, the informationprocessing apparatus including: circuitry configured to receive, from aterminal operated by a user, identification information that theterminal has acquired from the extraneous source; and transmit a requestfor execution of a process associated with the acquired identificationinformation to the intermediary device, the request for executioncausing the intermediary device to execute the process according to therequest for execution to control the device.

Example embodiments of the present invention include an informationprocessing system including the information processing apparatus, andthe intermediary device.

Example embodiments of the present invention include an informationprocessing method performed by the information processing apparatus, anda non-transitory recording medium storing a code for causing a computersystem to carry out the information processing method.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

A more complete appreciation of the disclosure and many of the attendantadvantages and features thereof can be readily obtained and understoodfrom the following detailed description with reference to theaccompanying drawings, wherein:

FIG. 1 is a diagram illustrating an example of a configuration of aninformation processing system according to a first embodiment;

FIG. 2 is a diagram illustrating an example of a hardware configurationof a server according to the first embodiment;

FIG. 3 is a diagram illustrating an example of a hardware configurationof a user terminal according to the first embodiment;

FIG. 4 is a diagram illustrating an example of a hardware configurationof an intermediary device according to the first embodiment;

FIG. 5 is a diagram for explaining an outline of the first embodiment;

FIG. 6 is a diagram illustrating an example of a functionalconfiguration of each device in the first embodiment;

FIGS. 7A and 7B (FIG. 7) are a sequence diagram for explaining anexample of a process procedure executed in response to activation of theintermediary device;

FIG. 8 is a diagram illustrating an example of a configuration of adevice information storage unit;

FIG. 9 is a diagram illustrating an example of a configuration of a taginformation storage unit;

FIG. 10 is a diagram illustrating an example of a configuration of anapplication information storage unit;

FIG. 11 is a sequence diagram for explaining an example of a processprocedure executed in response to proximity of a user terminal to a tagseal;

FIG. 12 is a diagram illustrating an example of a configuration of auser information storage unit;

FIG. 13 is a diagram illustrating a display example of an upload screen;

FIG. 14 is a sequence diagram for explaining an example of a processprocedure of a process for delivering image data from the user terminalto the intermediary device FIG. 15 is a diagram illustrating an exampleof a configuration of an information processing system in a secondembodiment;

FIG. 16 is a diagram illustrating an example of a hardware configurationof an intermediary device in the second embodiment;

FIG. 17 is a diagram illustrating an example of a functionalconfiguration of each device in the second embodiment;

FIG. 18 is a sequence diagram for explaining an example of a processprocedure of an advance preparation process in the second embodiment;

FIG. 19 is a diagram illustrating an example of a configuration of auser information storage unit in the second embodiment; and

FIGS. 20A and 20B (FIG. 20) are a sequence diagram for explaining anexample of a process procedure executed in response to proximity of theuser terminal to a source of a message beacon.

The accompanying drawings are intended to depict embodiments of thepresent invention and should not be interpreted to limit the scopethereof. The accompanying drawings are not to be considered as drawn toscale unless explicitly noted.

DETAILED DESCRIPTION

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the presentinvention. As used herein, the singular forms “a”, “an” and “the” areintended to include the plural forms as well, unless the context clearlyindicates otherwise.

In describing embodiments illustrated in the drawings, specificterminology is employed for the sake of clarity. However, the disclosureof this specification is not intended to be limited to the specificterminology so selected and it is to be understood that each specificelement includes all technical equivalents that have a similar function,operate in a similar manner, and achieve a similar result.

FIG. 1 is a diagram illustrating an example of a configuration of aninformation processing system according to a first embodiment. In aninformation processing system 1 illustrated in FIG. 1, a server 10communicates with one or more apparatus or devices in a user environmentE1 via a wide area network N1 such as the Internet. However, the networkN1 may be a network that can be accessed within a predetermined range,such as an intranet.

The user environment E1 is a system environment in an organization suchas a company in which output device such as one or more projectors 40and one or more intermediary devices 30 reside. The projector 40 is adevice that projects an input image on a projection plane, and is anexample of the output device. In the user environment E1, each projector40 is connected to the corresponding intermediary device 30. That is, inthis embodiment, the projector 40 and the intermediary device 30correspond one to one. The projector 40 and the intermediary device 30are connected via an interface conforming to a standard capable oftransmitting an image, such as High-Definition Multimedia Interface(HDMI) (registered trademark). For example, the projector 40 and theintermediary device 30 may be connected by a cable (for example, an HDMI(registered trademark) cable or the like) corresponding to theinterface. Alternatively, a connector of the intermediary device 30corresponding to the interface may be directly connected to a connectorof the projector 40 corresponding to the interface. For example, theintermediary device 30 is inserted into the connector of the projector40, and thus both may be connected. Alternatively, the intermediarydevice 30 and the projector 40 may be connected by wirelesscommunication, or may be connected via a network. Alternatively, inanother example, more than one device may be connected to oneintermediary device 30. For example, a plurality of projectors providedwith the Web API may be connected to one intermediary device 30.

By connecting the projector 40 and the intermediary device 30 asdescribed above, the intermediary device 30 can transmit an image to beprojected to the projector 40.

The intermediary device 30 is connected to the network N1 via a LAN orthe like in the user environment E1. The intermediary device 30 may bewirelessly connected to the LAN or the like in the user environment E1.The intermediary device 30 is provided with a Web browser, and by theWeb browser, executes a process according to a request for execution ofa process related to image data transmitted from the server 10, therebycontrolling the output device such as the projector 40 (for example,outputting an execution result of the process to the projector 40).Specifically, in the present embodiment, the intermediary device 30causes the projector 40 to execute an output (for example, projection)of the image data. That is, the intermediary device 30 mediates theoutput (for example, projection) of the image by the projector 40 forthe data transmitted from the server 10. For example, a computer such asan HDMI (registered trademark) dongle or a stick PC may be used as theintermediary device 30.

A user terminal 20 is an information processing terminal operated byeach user in the user environment E1. For example, a smartphone, atablet terminal, a PC, a mobile phone, or the like may be used as theuser terminal 20. Preferably, the user terminal 20 may be a mobileterminal. The user terminal 20 is connectable to the network N1 withoutvia the LAN or the like in the user environment E1 (for example, via amobile communication network, etc.). However, the user terminal 20 maybe connectable to a network in the user environment E1.

The server 10 is one or more computers that execute a process forexecuting output by the output device such as the projector 40 on imagedata specified in the user terminal 20, by a simple operation using theuser terminal 20. The server 10 may be installed in the user environmentE1.

FIG. 2 is a diagram illustrating an example of a hardware configurationof the server 10 according to the first embodiment. The server 10 ofFIG. 2 includes a drive device 100, an auxiliary memory 102, a memory103, a central processing unit (CPU) 104, an interface device 105, andthe like that are mutually connected by a bus B.

A program for executing a process in the server 10 is provided by arecording medium 101 such as a CD-ROM. When the recording medium 101storing the program is set in the drive device 100, the program isinstalled from the recording medium 101 into the auxiliary memory 102via the drive device 100. However, the program may not be installed fromthe recording medium 101, and may be downloaded from another computervia the network. The auxiliary memory 102 stores the installed programand also stores required files, data or the like.

When there is an instruction to start the program, the memory 103 readsout the program from the auxiliary memory 102 and stores the program.The CPU 104 executes a function related to the server 10 in accordancewith the program stored in the memory 103. The interface device 105 isused as an interface for connecting to the network.

FIG. 3 is a diagram illustrating an example of a hardware configurationof the user terminal 20 according to the first embodiment. In FIG. 3,the user terminal 20 includes a CPU 201, a ROM 202, a RAM 203, a touchpanel 204, an auxiliary memory 205, a near field communication device206, a digital camera 207, and the like.

The ROM 202 and the auxiliary memory 205 store programs and the likeinstalled in the user terminal 20. When there is an instruction to startthe program, the RAM 203 reads out the program from the ROM 202 or theauxiliary memory 205 and stores the program. The CPU 201 implements afunction related to the user terminal 20 in accordance with the programstored in the RAM 203.

The touch panel 204 is an electronic component including both an inputfunction and a display function, and performs display of information,reception of an input from a user, and the like. The touch panel 204includes a display 211, an input device 212, and the like.

The display 211 is a liquid crystal display or the like, and performs adisplay function of the touch panel 204. The input device 212 is anelectronic component including a sensor that detects contact of acontact object with the display 211. The contact object refers to anobject that contacts a contact surface (front surface) of the touchpanel 204. Examples of such an object include a user's finger and adedicated or general pen. The touch panel 204 may not be included, andthe user terminal 20 may include the display 211 and the input device212 separately. In addition, the display 211 may be externally connectedto the user terminal 20. Moreover, the input device 212 is not limitedto a sensor that detects a contact, and may also include an electroniccomponent such as a hardware key, a keyboard, and a mouse.

The near field communication device 206 is hardware for performing nearfield communication. In the first embodiment, the near fieldcommunication device 206 reads information stored in a near fieldcommunication (NFC) tag. That is, in the first embodiment, the nearfield communication device 206 is preferably an NFC reader. The digitalcamera 207 is a general digital camera including an image capturingfunction, and may be embedded in the user terminal 20 as an electroniccomponent, or may be externally connected to the user terminal 20.

FIG. 4 is a diagram illustrating an example of a hardware configurationof the intermediary device 30 in the first embodiment. The intermediarydevice 30 of FIG. 4 includes an auxiliary memory 301, a memory 302, aCPU 303, a communication interface 304, an image interface 305, and thelike.

A program for executing a process in the intermediary device 30 isinstalled in the auxiliary memory 301. The auxiliary memory 301 storesthe installed program and also stores required files, data or the like.

When there is an instruction to start the program, the memory 302 readsout the program from the auxiliary memory 301 and stores the program.The CPU 303 executes a function related to the intermediary device 30 inaccordance with the program stored in the memory 302. The communicationinterface 304 is a physical interface for connecting to the network. Theimage interface 305 is a physical interface for transmitting an image tothe projector 40.

FIG. 5 is a diagram for explaining an outline of the first embodiment.As illustrated in FIG. 5, for example, a seal-like NFC tag (hereinaftersimply referred to as “tag seal”) is attached to the projector 40. Inthe tag seal, information (hereinafter referred to as “tag information”)including a URL to be accessed first by the user terminal 20(hereinafter referred to as “initial access URL”) among URLs foraccessing the server 10 is stored. In the tag information, the initialaccess URL is assigned a registration ID as option information. Forexample, the tag information has a following format.

https://xxx.yyy.com/?tagid=Tag01

Here, a part of “XXX” in “tagid=XXX” (in the above, “Tag01”) correspondsto the registration ID. The registration ID is identificationinformation registered in the server 10. A different registration ID maybe allocated to each tag seal, or a same registration ID may beallocated to a plurality of tag seals. Meanwhile, a part“https://xxx.yyy.com/” (initial access URL) may be common to the taginformation stored in each tag seal used in the user environment E1. Theregistration ID may not be included in the initial access URL, and maybe stored separately from the initial access URL.

For example, the user terminal 20 is brought into close contact with thetag seal attached to the projector 40 by the user (S), the near fieldcommunication device 206 of the user terminal 20 reads the taginformation stored in the tag seal, thereby acquiring the tagInformation (S2). Subsequently, the user terminal 20 accesses the server10 that is a destination (“https://xxx.yyy.com”) of the initial accessURL included in the acquired tag information (S3). The registration IDand the like included in the acquired tag information are alsotransmitted to the server 10.

The server 10 controls an execution of a service registered in advancein association with the registration ID. For example, if the service isto cause a specific projector 40 to project image data captured by theuser terminal 20, the server 10 acquires from the user terminal 20 imagedata captured by the user terminal 20 and transmits the image data tothe intermediary device 30 associated with the registration ID (S4). Forexample, the server 10 transmits, to the user terminal 20, display dataof a screen prompting an upload of the image data and receives, from theuser terminal 20, the image data captured by the user terminal 20 inaccordance with an operation by the user via the screen, therebyacquiring the image data.

When the intermediary device 30 receives the image data from the server10, the intermediary device 30 renders the image data. As a result, arendering result is transmitted to the projector 40. The projector 40projects the rendering result (that is, the image data).

Therefore, the user can receive a service related to the output deviceas described above by a simple operation such as acquiring taginformation from an outside of the user terminal 20. For example, in theexample described above, the service as described above can be receivedby a simple operation such as bringing the user terminal 20 in proximityto the tag seal disposed in (attached to) the projector 40. As describedabove, the service to be executed is identified in accordance with theregistration ID. That is, a different service can be associated witheach registration ID.

In order to execute the process explained with reference to FIG. 5, theuser terminal 20, the intermediary device 30, and the server 10 includefunctional configurations as illustrated in FIG. 3.

FIG. 6 is a diagram illustrating an example of a functionalconfiguration of each device in the first embodiment. In FIG. 6, theuser terminal 20 includes an information acquirer 21 and a browser unit22. These units are implemented by instructions of the CPU 201 accordingto one or more programs installed in the user terminal 20.

The information acquirer 21 acquires tag information (initial access URLincluding the registration ID) from the tag seal with the use of thenear field communication device 206, and activates the browser unit 22with the tag information as input information. The information acquirer21 may be implemented by a process that a part of an operating system(OS) of the user terminal 20 causes the CPU 201 to execute.

The browser unit 22 is, for example, a general Web browser, and executesa process according to HyperText Markup Language (HTML) data, a script(for example, JavaScript (registered trademark)), and the like. Thebrowser unit 22 transmits, to an application determiner 12 of the server10 corresponding to the initial access URL included in the taginformation notified as input information from the information acquirer21, the registration ID or the like included in the tag information URL.The browser unit 22 also accesses an application associated with theregistration ID among applications included in the server 10, inaccordance with a redirect request which is a response from theapplication determiner 12 to the access to the initial access URL. Thebrowser unit 22 acquires, from the application, data (HTML data, script,etc.) indicating a request for the user terminal 20 to execute aprocess.

The intermediary device 30 includes a communication controller 31, abrowser manager 32, a browser unit 33, and the like. These units areimplemented by instructions that one or more programs installed in theintermediary device 30 cause the CPU 303 to execute.

The communication controller 31 connects a bidirectional communicationpath with a distribution unit 11 of the server 10 (establishes acommunication session), and functions as an end point on theintermediary device 30 side in the communication path (communicationsession). By communication via the communication path (communicationsession), a state of the intermediary device 30 is notified to theserver 10 and a notification that image data to be projected by theintermediary device 30 onto the projector 40 has been input to theserver 10 (in the present embodiment, a notification that the image datahas been uploaded from the user terminal 20) can be received from theserver 10.

The browser manager 32 activates the browser unit 33 in, for example, akiosk mode. The kiosk mode is a mode in which a use of the intermediarydevice 30 is limited to a display of a Web page. The kiosk mode ismerely an example, and other modes may be used as long as the Web pagecan be displayed.

The browser unit 33 is, for example, a general Web browser, and executesa process according to HTML data, a script, and the like. The browserunit 33 accesses the initial access URL (that is, the applicationdeterminer 12 of the server 10) in response to the activation. In doingso, identification information of the browser unit 33 (hereinafterreferred to as “browser ID”) is assigned as option information to theinitial access URL. The browser unit 33 also accesses an applicationassociated with the browser ID among the applications included in theserver 10, in accordance with a redirect request which is a responsefrom the application determiner 12 to the access to the initial accessURL. The browser unit 33 acquires, from the application, data (HTMLdata, script, etc.) indicating a request for the intermediary device 30to execute a process.

The server 10 includes the distribution unit 11, the applicationdeterminer 12, an upload application 13, an output application 14, andthe like. These units are implemented by processes that one or moreprograms installed in the server 10 cause the CPU 104 to execute. Theserver 10 also includes an application information storage unit 121, adevice information storage unit 122, a user information storage unit123, a tag information storage unit 124, and the like. These storageunits can be implemented with the use of, for example, the auxiliarymemory 102 or a storage device connectable to the server 10 via thenetwork.

The distribution unit 11 receives image data to be an input for aservice associated with the registration ID, from an input source of theimage data, and notifies an output destination of the image data in theservice of an input of the image data. In addition, the distributionunit 11 transmits the image data to the output destination in responseto a request from the output destination. In the present embodiment, theinput source is the user terminal 20, and the output destination is theintermediary device 30.

The application determiner 12 determines an application corresponding tothe initial access URL. The application determiner 12 determines anapplication corresponding to the option information (registration ID orbrowser ID) assigned to the initial access URL with reference to the taginformation storage unit 124 in response to the access to the initialaccess URL. The application determiner 12 transmits a response includinga redirect request including the URL for the determined application, toa source that has accessed the initial access URL. In the presentembodiment, with regard to an access from the user terminal 20 that isthe input source of the image data, the URL of the upload application 13is determined as an application corresponding to the registration ID. Inaddition, with regard to an access from the intermediary device 30 thatis the output destination of the image data, the URL of the outputapplication 14 is determined as an application corresponding to thebrowser ID.

The upload application 13 and the output application 14 are an exampleof an application included in the server 10 in the present embodiment.The upload application 13 is an application for causing the userterminal 20 to upload the image data. Specifically, the uploadapplication 13 transmits, to the user terminal 20, HTML data, a script,and the like for executing an upload of the image data. The outputapplication 14 is an application for causing the intermediary device 30to execute acquisition (download) and output of the image data uploadedfrom the user terminal 20. Specifically, the output application 14transmits, to the intermediary device 30, HTML data, a script, and thelike for causing the intermediary device 30 to execute the acquisitionand the output.

Information (for example, a URL, etc.) related to each of theapplications (the upload application 13 and the output application 14 inthe present embodiment) included in the server 10 is stored in theapplication information storage unit 121.

The user information storage unit 123 stores identification informationand the like of a user who can use the application in the server 10.

The device information storage unit 122 stores, for each intermediarydevice 30 disposed in the user environment E1, information indicatingthe state of the intermediary device 30.

The tag information storage unit 124 stores, for each registered ID,identification information of an application executing an input processof the image data, identification information of an applicationexecuting an output process of the image data, identificationinformation of the browser unit 33 of the intermediary device 30 that isthe input destination of the image data, and the like.

The process procedure executed in the information processing system 1will be described below. FIG. 7 is a sequence diagram for explaining anexample of a process procedure executed in response to activation of theintermediary device 30.

In response to user operation of turning on the intermediary device 30(S101), the communication controller 31 establishes a communication path(session) with the distribution unit 11 for asynchronously receiving arequest from the distribution unit 11 of the server 10 (S102). In doingso, the communication controller 31 notifies the distribution unit 11 ofa communication ID which is identification information of thecommunication controller 31. The distribution unit 11 updates the deviceinformation storage unit 122 based on the notified communication ID(hereinafter, referred to as “target communication ID”).

FIG. 8 is a diagram illustrating an example of a configuration of thedevice information storage unit 122. In FIG. 8, the device informationstorage unit 122 stores a communication ID, address information, stateinformation, a browser ID, a browser state, and the like in associationwith a tenant ID. The tenant ID is identification information of acontractor (tenant) of a usage contract of a service provided by theserver 10. For example, the user environment E1 may correspond to onetenant. The communication ID is identification information of thecommunication controller 31 of each intermediary device 30 disposed inthe tenant related to the tenant ID. When the intermediary device 30includes one communication controller 31, the communication ID may beidentification information for identifying the intermediary device 30.The address information is a local IP address of the intermediary device30. The state information is information indicating whether thecommunication controller 31 related to the communication ID is beingconnected to the server 10 or not (in a state where the communicationpath is established or not established). The browser ID isidentification information of the browser unit 33 corresponding to thecommunication controller 31 related to the communication ID. In thepresent embodiment, the browser ID is identification information of thebrowser unit 33 included in the same intermediary device 30 in which thecommunication controller 31 related to the communication ID is included.The browser state is information indicating an activation state of thebrowser unit 33 related to the browser ID.

For example, if the target communication ID notified to the distributionunit 11 is “Eg001-01”, the state information corresponding to thecommunication ID in the device information storage unit 122 is changedto “connected” as illustrated in FIG. 8.

Subsequently, the communication controller 31 searches for the browsermanager 32 with the use of, for example, Simple Network ManagementProtocol (SNMP) or the like in order to acquire the browser ID (S103),and acquires, from the found browser manager 32, the browser ID that isidentification information of the browser unit 33 managed by the browsermanager 32 (S104). In the present embodiment, an example in which thecommunication controller 31 and the browser manager 32 are included inthe intermediary device 30 is illustrated, and in order for thecommunication controller 31 included in the intermediary device 30 tocommunicate with the browser manager 32 included in another intermediarydevice 30 via a same network to thereby make a plurality of browsermanagers 32 and browser units 33 also available, the browser managers 32are searched for with the use of the SNMP or the like. Therefore, thebrowser manager 32 may not be searched for, and an acquisitiondestination (the browser manager 32) from which the communicationcontroller 31 acquires the browser ID may be set in advance.

Subsequently, the communication controller 31 transmits, to thedistribution unit 11, a notification that the browser unit 33 (in thepresent embodiment, the browser unit 33 of the intermediary device 30)corresponding to the acquired browser ID has become available, whilespecifying the browser ID of the browser unit 33 (hereinafter referredto as “target browser ID”) (S105). In response to reception of thenotification, the distribution unit 11 updates the device informationstorage unit 122 (FIG. 8) based on the target browser ID specified inthe notification. Specifically, in the device information storage unit122, a value of the browser state corresponding to the target browser IDis updated from “power off” to “power on”.

Subsequently, the communication controller 31 requests the browsermanager 32 to activate the browser unit 33 related to the target browserID while specifying the target browser ID and the initial access URL(S106). As described above, the initial access URL refers to a URL thatthe browser unit 33 is to first access, and is set in advance in thebrowser manager 32.

In response to the request from the communication controller 31, thebrowser manager 32 activates the browser unit 33 related to the targetbrowser ID in the kiosk mode (S107). In doing so, the browser manager 32inputs the initial access URL to the browser unit 33. The browser unit33 transmits an HTTP request to the input initial access URL in responseto the activation in the kiosk mode (S108). The HTTP request includesthe target browser ID.

In response to reception of the HTTP request, the application determiner12 of the server 10 transmits, to the browser unit 33, a response (HTTPresponse) including a redirect request (S109). The redirect requestincludes a URL of an application associated with the browser ID as aredirect destination. In addition, the redirect request includes acommunication URL and the target browser ID included in the HTTP requestas notification information for the redirect destination. Thecommunication URL is a URL of the communication controller 31.

The application determiner 12 identifies the URL of the applicationassociated with the target browser ID with reference to the taginformation storage unit 124 and the application information storageunit 121.

FIG. 9 is a diagram illustrating an example of a configuration of thetag information storage unit 124. In FIG. 9, the tag information storageunit 124 stores a registration ID, an In application ID, an Outapplication ID, and a browser ID in association with one other.

The In application ID is an ID of an application that controls an inputof image data in a service corresponding to the registration ID(hereinafter referred to as an “application ID”). The “AP_Upload”indicates an application ID of the upload application 13. The Outapplication ID is an application ID of an application that controls anoutput of image data in the service corresponding to the registrationID. The “AP_PhotoShow” indicates an application ID of the outputapplication 14. The browser ID is the browser ID of the browser unit 33corresponding to the registration ID.

FIG. 10 is a diagram illustrating an example of a configuration of theapplication information storage unit 121. In FIG. 10, the applicationinformation storage unit 121 stores an application ID, an applicationtype, a URL, and the like for each application included in the server10.

The application type indicates a type based on a relation with the imagedata for an application related to the application ID. The “in”indicates that the application controls an input of image data(corresponding to the above-described In application ID). The “Out”indicates that the application controls an output of image data(corresponding to the above-described Out application ID). The URL is aURL of the application related to the application ID.

Therefore, the application determiner 12 refers to the tag informationstorage unit 124 to identify the Out application ID associated with thetarget browser ID, and refers to the application information storageunit 121 to identify the URL associated with the Out application ID.Here, it is assumed that the target browser ID is “BROWSER1”. In thiscase, the URL of the application (output application 14) whoseapplication ID is the “AP_PhotoShow” (hereinafter, “output applicationURL”) is identified.

In addition, the application determiner 12 automatically generates thecommunication URL of the communication controller 31 related to thetarget communication ID on the basis of the address informationassociated with the target browser ID in the device information storageunit 122 (FIG. 8).

Subsequently, in accordance with the redirect request, the browser unit33 transmits (redirects) an HTTP request to the output application URLthat is the redirect destination (i.e., the output application 14)(S110). The HTTP request includes the communication URL and the browserID included in the redirect request.

In response to the HTTP request, the output application 14 transmits, tothe browser unit 33, a response including a script (photo.js) forcausing the browser unit 33 to execute connection to the communicationURL included in the HTTP request and display data (photo. html) forcausing the browser unit 33 to render a user interface for outputtingimage data (for example, a slide show) (S11). The script and the displaydata are an example of data indicating a request for the intermediarydevice 30 to execute a process.

In response to reception of the response, the browser unit 33 executesthe script (photo.js) included in the response to establish acommunication path with the communication controller 31 identified bythe communication URL (S112). The communication path is a communicationpath for the communication controller 31 to transmit, to the browserunit 33, a notification received from the server 10. For thecommunication path, websocket may be used.

Subsequently, the browser unit 33 renders a screen (hereinafter referredto as “projection screen”) based on the display data (photo, html)included in the response, in a predetermined area (for example, a videomemory) of the memory 103 (S13). For example, the projection screen is ascreen that functions as a frame to which the image data distributedfrom the server 10 is applied. The content rendered by the browser unit33 (projection screen) is output to the projector 40 via the HDMI(registered trademark) or the like and is output (projected) by theprojector 40.

FIG. 11 is a sequence diagram for explaining an example of a processprocedure executed in response to proximity of the user terminal 20 tothe tag seal.

For example, when the user brings the user terminal 20 close to the tagseal attached to the projector 40 (for example, when the terminal 20 isheld over the tag seal) (S201), the information acquirer 21 acquires thetag information stored in the tag seal via near field communicationusing the near field communication device 206 (S202 and S203). The taginformation includes the initial access URL to which the registration ID(hereinafter referred to as “target registration ID”) is assigned asoption information. In the present embodiment, it is assumed that avalue of the target registration ID is “Tag 01”.

Subsequently, the information acquirer 21 activates the browser unit 22with the tag information as input information on the basis of a factthat the tag information includes the URL (S204).

In response to the activation, the browser unit 22 automaticallytransmits an HTTP request to the application determiner 12 correspondingto the initial access URL included in the tag information that is theinput information (S205). The HTTP request includes account informationas option information in addition to the target registration ID. Theaccount information is information including identification informationof the user of the user terminal 20 (hereinafter referred to as “userID”) and the tenant ID of the user environment E1 to which the userbelongs, or is information by which the user ID and the tenant ID can beidentified. For example, a Cookie or the like may be used as the accountinformation.

In response to reception of the HTTP request, the application determiner12 of the server 10 authenticates the account information included inthe HTTP request. If the authentication is successful, step S206 andsubsequent steps are executed. The authentication is performed on thebasis of, for example, whether the account information included in theHTTP request is registered in the user information storage unit 123.

FIG. 12 is a diagram illustrating an example of a configuration of theuser information storage unit 123. In FIG. 12, the user informationstorage unit 123 stores the tenant ID, the user ID and the like for eachuser who is permitted to use an application of the server 10.

If the authentication is successful, the application determiner 12transmits a response (HTTP response) including a redirect request to thebrowser unit 22 (S206). The redirect request includes a URL of theupload application 13 (hereinafter referred to as “upload applicationURL”) related to the In application ID (“AP_Upload”) stored in the taginformation storage unit 124 (FIG. 9) in association with the targetregistration ID (“Tag01”) as the redirect destination. The uploadapplication URL can be identified with reference to the applicationinformation storage unit 121 (FIG. 10).

In accordance with the redirect request, the browser unit 22 transmitsan HTTP request (redirect) to the upload application URL that is theredirect destination (i.e., the upload application 13) (S207).

In response to the HTTP request, the upload application 13 transmits, tothe browser unit 22, a response including display data (upload.html) ofa screen (hereinafter referred to as “upload screen”) related to anupload of image data to the distribution unit 11 of the server 10 and ascript (upload.js) for causing the user terminal 20 to execute theupload in accordance with an operation on the upload screen (S208). Thescript and the display data are an example of data indicating a requestfor the user terminal 20 to execute a process.

In response to reception of the response, the browser unit 22 generatesan upload screen on the basis of the display data (upload.html) anddisplays the upload screen on the display 211 (S209).

FIG. 13 is a diagram illustrating a display example of the uploadscreen. In FIG. 13, an upload screen 510 includes a button 511 and thelike. The button 511 is a screen for receiving an instruction to startan image capturing operation. The user selects the button 511 to performimage capturing. As a result, the captured image data is displayed onthe display 211.

FIG. 14 is a sequence diagram for explaining an example of a processprocedure of a process for delivering image data from the user terminal20 to the intermediary device 30.

When the user performs a predetermined operation (for example, swipe,etc.) corresponding to an upload instruction on the image data(hereinafter referred to as “target image data”) displayed on thedisplay 211 of the user terminal 20 (S301), the browser unit 22transmits (uploads) target image data (photo.jpeg) and a targetregistration ID to the distribution unit 11 of the server 10 inaccordance with a definition of the script (upload.js) (S302). Inresponse to reception of the target image data and the targetregistration ID, the distribution unit 11 allocates identificationinformation (hereinafter referred to as “image ID”) to the target imagedata, and stores the target image data in, for example, the auxiliarymemory 102 or the like, in association with the image ID (hereinafterreferred to as “target image ID”).

Subsequently, the distribution unit 11 identifies the browser ID (targetbrowser ID) stored in the tag information storage unit 124 (FIG. 9) inassociation with the target registration ID. The distribution unit 11uses the communication path established with the communicationcontroller 31 related to the communication ID (target communication ID)stored in the device information storage unit 122 (FIG. 8) inassociation with the target browser ID (the communication pathestablished in step S102 of FIG. 7), to transmit, to the communicationcontroller 31, a notification that the image data has been uploaded(hereinafter referred to as “upload notification”) (S303). The uploadnotification includes the target image ID and the target browser ID.

In response to reception of the upload notification, the communicationcontroller 31 uses the communication path established between thebrowser unit 33 corresponding to the browser ID included in the uploadnotification and the communication controller 31 (the communication pathestablished in step S112 of FIG. 71), to notify the browser unit 33 ofthe target image ID included in the upload notification (S304).

In response to the notification from the communication controller 31,the browser unit 33 transmits a request for acquisition of the imagedata to the distribution unit 11 in accordance with the definition ofthe script (photo.js) (S305). The acquisition request includes thetarget image ID. In response to the acquisition request, thedistribution unit 11 transmits, to the browser unit 33, a responseincluding the image data (photo. jpeg) associated with the target imageID included in the acquisition request (306).

In response to reception of the image data, the browser unit 33 rendersthe image data in a predetermined area (for example, a video memory) ofthe memory 103 so as to apply the image data in the projection screenrendered in step S113 of FIG. 7 (S307). The rendering content istransmitted to the projector 40 by the image interface 305 or thecommunication interface 304 of the intermediary device 30. As a result,the projector 40 projects the rendering content.

By the above-described process procedure, a service, in which the imagedata is output by the output device such as the projector 40 each timethe user terminal 20 captures the image data, is implemented. Forexample, by using the service in a venue such as a party, a seminar, andan exhibition, it is possible to sequentially display and output imagedata captured in the venue on a large display screen.

While an example in which the device connected to the intermediarydevice 30 is the projector 40 is illustrated above, other device such asa digital signage, an electronic whiteboard, a display, or a printer maybe connected to the intermediary device 30 as an alternative to theprojector 40. In this case, the rendering content of the intermediarydevice 30 may be displayed on the digital signage, the electronicwhiteboard, the display or the like, or may be printed by the printer.

In addition, while an example in which the tag seal is attached to theprojector 40 associated with the tag seal is illustrated above forconvenience of explanation, there is no limitation on the location wherethe tag seal is attached. For example, the tag seal may be attached toany position in a room in which the projector 40 is disposed.

As described above, according to the first embodiment, by bringing theuser terminal 20 close to the tag seal, the user can cause the device(for example, the projector 40) connected to the intermediary device 30to execute a process set in advance in association with the tag seal(registration ID). That is, the user does not need to directly operatethe projector 40 or the like, and can operate the projector 40 or thelike by an operation on the user terminal 20. Therefore, operability ofdevice such as the projector 40 can be improved.

In addition, a screen displayed on the user terminal 20 is based ondisplay data such as HTML data distributed from the server 10, and adegree of dependence on the device associated with the tag seal is low.Therefore, according to the present embodiment, it is possible to reduceopportunity for the user to operate a different user interface such asan operation panel depending on the device, thereby enabling the user touse each device by a highly uniform operation across a plurality ofpieces of device.

In addition, even in a case of device that does not include a networkfunction, if the device includes an interface for transmitting imagedata, the present embodiment can be applied by interposing theintermediary device 30 between the server 10 and the device (theprojector 40). Moreover, when it is desired to switch the device towhich the image data is output, the device connected to the intermediarydevice 30 may be switched, and there is no need to change settinginformation in the server 10.

Further, in the present embodiment, a program included in a generalsmart phone or the like may also be installed in the user terminal 20,and a special application need not be installed in the user terminal 20.

Furthermore, since the intermediary device 30 and the device may beconnected by an interface for transmitting image data, for example,setting for connection by a wireless LAN via a router or for connectionby a wired LAN is not required.

While, in the first embodiment, an example in which the NFC tag is usedas an example of an external recording medium storing the taginformation is illustrated, the tag information may be acquired by amethod other than the near field communication, so long as the userterminal 20 can acquire the tag information from the outside. Forexample, a seal on which a barcode or a two-dimensional code recordingthe tag information is printed may be used as an alternative to the tagseal. In this case, the user terminal 20 may acquire the tag informationwith the use of a bar code reader or a two-dimensional code reader, thedigital camera 207 or the like. The bar code or the two-dimensional codemay not be printed on the seal, and may be displayed on a display of theoutput device, for example, or may be printed on the output device perse or an external recording medium other than the seal. The tag seal ofthe NFC tag described above is merely an example, and similarly, theexternal recording medium other than the seal may include the NFC tag.

Alternatively, the user terminal 20 may receive a sound wave transmittedfrom a transmitting device installed in the periphery of the outputdevice or included in the output device per se and a beacon that will bedescribed later, and acquire the tag information embedded in thereceived sound wave or beacon.

Alternatively, the user terminal 20 may access, via a network, a deviceinstalled in the periphery of the output device or the output device perse to acquire the stored tag information.

Alternatively, the user terminal 20 may acquire the tag information froman external recording medium (for example, a seal) on which an image isprinted. In this case, the user terminal 20 may input the image by thedigital camera 207 and extract the tag information from a tint block orthe like embedded in the image. A known technique may be used to embedinformation in an image using a tint block or the like or to extractinformation from the tint block.

Next, a second embodiment will be described. In the second embodiment,different points from the first embodiment will be described. Therefore,points that are not particularly mentioned may be the same as in thefirst embodiment.

In the second embodiment, a message application such as LINE (registeredtrademark) is used. In addition, in the second embodiment, a beacon fora message application 23 (a beacon based on near field communicationsuch as Bluetooth (registered trademark) Low Energy (BLE)) including theregistration ID is used as an alternative to the tag seal. Hereinafter,the beacon is referred to as a “message beacon”.

FIG. 15 is a diagram illustrating an example of a configuration of aninformation processing system in the second embodiment. In FIG. 15, sameparts as those in FIG. 1 are denoted by same reference numerals, and adescription thereof is omitted.

In FIG. 15, a message service 50 is further connected to the network N1.The message service 50 is one or more computers that provide a serviceto the message application 23 (function as a server for the messageapplication 23). A user of the message application 23 performs userregistration in the message service 50 and receives issuance of a userID for the message application 23.

FIG. 16 is a diagram illustrating an example of a hardware configurationof the intermediary device 30 in the second embodiment. In FIG. 16, sameparts as those in FIG. 4 are denoted by same reference numerals, and adescription thereof is omitted. In FIG. 16, the intermediary device 30further includes a near field communication device 306. The near fieldcommunication device 306 is hardware for performing near fieldcommunication such as BLE. In the present embodiment, the near fieldcommunication device 306 is used to transmit the message beacon.

FIG. 17 is a diagram illustrating an example of a functionalconfiguration of each device in the second embodiment. In FIG. 17, sameparts as those in FIG. 6 are denoted by same reference numerals, and adescription thereof is omitted.

In FIG. 17, the user terminal 20 further includes the messageapplication 23. The message application 23 is as described above.

The server 10 further includes a message bot 15. The message bot 15 is aprogram (Bot) that automatically executes transmission and reception ofmessages with the message application 23.

FIG. 18 is a sequence diagram for explaining an example of a processprocedure of an advance preparation process in the second embodiment. Inthe second embodiment, the process procedure illustrated in FIG. 18 isperformed as an advance preparation.

In step S401, the message bot 15 is registered as a user in the messageservice 50, and a user ID (hereinafter referred to as “message bot ID”)is issued to the message bot 15.

Then, the message bot ID is notified to the user of the user terminal 20(S402). For example, a mail, a QR code (registered trademark), or thelike including the message bot ID is transmitted to the user terminal20.

When the user inputs the notified message bot ID to the messageapplication 23 of the user terminal 20 to instruct to register as afriend (S403), the message application 23 transmits, to the messageservice 50, a friend registration request including the user ID of theuser related to the message application 23 (hereinafter referred to as“message user ID”) and the input message bot ID (S404). The messageapplication 23 can immediately receive the notification (message) fromthe message bot 15 by registering as a friend.

In response to reception of the friend registration request, the messageservice 50 notifies the message bot 15 related to the message bot IDincluded in the friend registration request that the user related to themessage user ID included in the friend registration request hasregistered as a friend (S405).

Subsequently, in order for the message beacon to be transmitted from theintermediary device 30, the message bot 15 transmits a beaconapplication including the message bot ID to the message service 50, andreceives, from the message service 50, issuance of a HardwareID(hereinafter referred to as “HID”) to be included in the message beacon(S406).

Subsequently, the message bot 15 transmits a beacon registration requestfor transmitting the message beacon, to the communication controller 31of the intermediary device 30 related to a tenant ID corresponding tothe message user ID that has registered the message bot 15 as a friend(S407). The registration request includes the HID, a browser IDcorresponding to the tenant ID, and a registration ID corresponding tothe browser ID. The tenant ID corresponding to the message user ID canbe identified with reference to the user information storage unit 123.

FIG. 19 is a diagram illustrating an example of a configuration of theuser information storage unit 123 in the second embodiment. Asillustrated in FIG. 19, in the second embodiment, the message user ID isassociated with each set of the tenant ID and the user ID in the userinformation storage unit 123. Therefore, the message bot 15 can identifythe tenant ID corresponding to the message user ID with reference to theuser information storage unit 123.

In addition, the browser ID corresponding to the tenant ID can beidentified with reference to the device information storage unit 122(FIG. 8). Moreover, the registration ID corresponding to the browser IDcan be identified with reference to the tag information storage unit 124(FIG. 9).

Subsequently, in response to reception of the registration request, thecommunication controller 31 requests the browser manager 32corresponding to the browser unit 33 related to the browser ID includedin the registration request, to transmit a beacon including the targetregistration ID and the HID (S408). Subsequently, the browser manager 32requests the near field communication device 306 to transmit the messagebeacon including the target registration ID and the HID (S409). As aresult, the near field communication device 306 of the intermediarydevice 30 starts transmitting the message beacon including the targetregistration ID and the HID.

FIG. 20 is a sequence diagram for explaining an example of a processprocedure executed in response to proximity of the user terminal 20 to asource of the message beacon. The process procedure of FIG. 7 isexecuted before execution of the process procedure of FIG. 20.

When the user brings the user terminal 20 close to the intermediarydevice 30 that is transmitting the message beacon (S501), theinformation acquirer 21 of the user terminal 20 receives the messagebeacon with the use of the near field communication device 206 (S502),and acquires the HID (hereinafter referred to as “target HID”) and theregistration ID (hereinafter referred to as “target registration ID”)included in the message beacon (S503). That is, in the secondembodiment, the near field communication device 206 is hardware capableof receiving a beacon based on BLE or the like transmitted by the nearfield communication device 306 of the intermediary device 30. In thepresent embodiment, it is assumed that a value of the targetregistration ID is “Tag 01”.

Subsequently, the information acquirer 21 notifies the messageapplication 23 of the user terminal 20 of the content (the target HIDand the target registration ID) of the message beacon on the basis of afact that a format of the message beacon corresponds to the messageapplication 23 (S504). In response to the notification of the content ofthe message beacon, the message application 23 transmits, to the messageservice 50, a notification that the message beacon has been received(hereinafter, referred to as “beacon reception notification”) (S505). Indoing so, the message application 23 includes the message user ID of theuser of the user terminal 20, the target HID and the target registrationID in the beacon reception notification.

The message service 50 transmits the beacon reception notification tothe message bot 15 corresponding to the target HID (S506). That is, inthe message service 50, the message bot 15 or the like that has receivedthe issuance of the HID is managed in association with the HID. Thebeacon reception notification further includes a message ID foridentifying the beacon reception notification. The message service 50stores the content (message user ID, etc.) included in the beaconreception notification, in association with the message ID.

In response to reception of the beacon reception notification, themessage bot 15 transmits, to the message service 50, a response to thebeacon reception notification (S507). The response includes a one-shotID and the initial access URL, in addition to the message ID and thetarget registration ID included in the beacon reception notification.The initial access URL is a URL for the application determiner 12 asdescribed in the first embodiment. In the second embodiment, the initialaccess URL is set in advance in the message bot 15. In addition, theone-shot ID is identification information for limiting a period forlogin to the server 10 and is automatically generated by the message bot15. For example, the one-shot ID may be a value based on a current dateand time, or may be a value based on a date and time, or the likeindicating a time limit for login. When the period for login to theserver 10 is not limited, the one-shot ID may not be generated.

Subsequently, in response to the response from the message bot 15, themessage service 50 transmits, to the message user ID stored inassociation with the message ID included in the response, a messageincluding the content of the response from the message bot 15 (theinitial access URL, the one-shot ID, the message user ID, the targetregistration ID, etc.) as a message from the message bot 15 (S508). Forexample, the message includes an operation button associated with a linkof the initial access URL including the one-shot ID, the message userID, and the target registration ID as option information.

In response to reception of the message, the message application 23 ofthe user terminal 20 of the user corresponding to the message user IDdisplays the message on the display 211 (S509). As a result, the usercan confirm the message.

Subsequently, when the user presses the operation button included in themessage (S510), the message application 23 automatically activates thebrowser unit 22 with the initial access URL indicated by the linkassociated with the operation button, as input information (S511). Whenthe message application 23 includes a browser inside, the browser may beused as the browser unit 22.

In response to the activation, the browser unit 22 automaticallytransmits an HTTP request to the application determiner 12 correspondingto the initial access URL included in the input information (S512). TheHTTP request includes option information (the one-shot ID, the messageuser ID, and the target registration ID) of the initial access URL.

In response to reception of the HTTP request, the application determiner12 of the server 10 authenticates the message ID and the one-shot IDincluded in the HTTP request. For example, if the message user ID isstored as the message user ID of any user in the user informationstorage unit 123 (FIG. 19) and the one-shot ID has not expired, theauthentication is successful, otherwise the authentication fails.

If the authentication is successful, processes similar to steps S206 toS209 in FIG. 11 are performed (S513 to S516). As a result, the uploadscreen 510 (FIG. 13) is displayed on the display 211 of the userterminal 20.

Then, in accordance with capturing of image data by the user terminal20, the process procedure described with reference to FIG. 14 isperformed.

As described above, according to the second embodiment, the same effectas that of the first embodiment can be obtained without using the tagseal.

The server 10, the intermediary device 30, the output device such as theprojector 40, the user terminal 20, and the message service 50 in theabove embodiments may be constructed by a single computer or a pluralityof computers to which respective units (functions or means) are dividedand arbitrarily allocated.

In each of the above embodiments, the application determiner 12 is anexample of the first receiving means. The upload application 13 is anexample of second receiving means. The output application 14 and thedistribution unit 11 are an example of transmitting means. The server 10is an example of an information processing apparatus, which may beimplemented by one or more computers.

The above-described embodiments are illustrative and do not limit thepresent invention. Thus, numerous additional modifications andvariations are possible in light of the above teachings. For example,elements and/or features of different illustrative embodiments may becombined with each other and/or substituted for each other within thescope of the present invention.

Any one of the above-described operations may be performed in variousother ways, for example, in an order different from the one describedabove.

The present invention can be implemented in any convenient form, forexample using dedicated hardware, or a mixture of dedicated hardware andsoftware. The present invention may be implemented as computer softwareimplemented by one or more networked processing apparatuses. The networkcan comprise any conventional terrestrial or wireless communicationsnetwork, such as the Internet. The processing apparatuses can compromiseany suitably programmed apparatuses such as a general purpose computer,personal digital assistant, mobile telephone (such as a WAP or3G-compliant phone) and so on. Since the present invention can beimplemented as software, each and every aspect of the present inventionthus encompasses computer software implementable on a programmabledevice.

The computer software can be provided to the programmable device usingany storage medium for storing processor readable code such as a floppydisk, hard disk, CD ROM, magnetic tape device or solid state memorydevice. The hardware platform includes any desired kind of hardwareresources including, for example, a central processing unit (CPU), arandom access memory (RAM), and a hard disk drive (HDD). The CPU may beimplemented by any desired kind of any desired number of processor. TheRAM may be implemented by any desired kind of volatile or non-volatilememory. The HDD may be implemented by any desired kind of non-volatilememory capable of storing a large amount of data. The hardware resourcesmay additionally include an input device, an output device, or a networkdevice, depending on the type of the apparatus. Alternatively, the HDDmay be provided outside of the apparatus as long as the HDD isaccessible. In this example, the CPU, such as a cache memory of the CPU,and the RAM may function as a physical memory or a primary memory of theapparatus, while the HDD may function as a secondary memory of theapparatus.

Each of the functions of the described embodiments may be implemented byone or more processing circuits or circuitry. Processing circuitryincludes a programmed processor, as a processor includes circuitry. Aprocessing circuit also includes devices such as an application specificintegrated circuit (ASIC), digital signal processor (DSP), fieldprogrammable gate array (FPGA), and conventional circuit componentsarranged to perform the recited functions.

1. An information processing apparatus communicably connected with an intermediary device capable of communicating with at least one device, the information processing apparatus comprising: circuitry configured to receive, from a terminal operated by a user, identification information that the terminal has acquired from the extraneous source; and transmit a request for execution of a process associated with the acquired identification information to the intermediary device, the request for execution causing the intermediary device to execute the process according to the request for execution to control the device.
 2. The information processing apparatus according to claim 1, wherein the circuitry identifies an intermediary device associated with the acquired identification information, and transmits the request for execution to the identified intermediary device.
 3. The information processing apparatus according to claim 2, wherein the circuitry is further configured to: receive image data from the terminal; and transmit the received image data to the intermediary device, wherein the request for execution causes the intermediary device to execute the process according to the request for execution on the transmitted image data to control the device.
 4. An information processing system comprising: an information processing apparatus comprising first circuitry; and an intermediary device communicably connected with the information processing apparatus and configured to communicate with at least one device, the intermediary device comprising second circuitry, the second circuitry being configured to: receive, from a terminal operated by a user, identification information that the terminal has acquired from the extraneous source; and transmit a request for execution of a process associated with the acquired identification information to the intermediary device, the first circuitry being configured to: executes the process according to the request for execution transmitted from the information processing apparatus to control the device.
 5. The information processing system according to claim 4, wherein the second circuitry of the intermediary device further receives image data transmitted from the terminal, from the information processing apparatus, and executes the process according to the request for execution on the received image data.
 6. The information processing system according to claim 5, wherein the second circuitry of the intermediary device causes the device to output an image based on the received image data.
 7. The information processing system according to claim 4, further comprising the terminal, wherein the terminal acquires the identification information from the extraneous source via near field communication.
 8. An information processing method executed by an information processing apparatus communicably connected with an intermediary device capable of communicating with at least one device, the method comprising: receiving, from a terminal operated by a user, identification information acquired that the terminal has acquired from the extraneous source; and transmitting a request for execution of a process associated with the acquired identification information to the intermediary device, the request for execution causing the intermediary device to execute the process according to the request for execution to control the device.
 9. The information processing method according to claim 8, wherein the transmitting includes: identifying an intermediary device associated with the acquired identification information; and transmitting the request for execution to the identified intermediary device.
 10. The information processing method according to claim 8, further comprising: receiving image data from the terminal; and transmitting the received image data to the intermediary device, the request for execution causes the intermediary device to execute the process according to the request for execution on the transmitted image data to control the device. 